Add code page support to JvCreateProcess for stdout and stderr #188
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When JvCreateProcess receives messages from stdout and stderr of a console application, I want to be able to apply a specified codepage to the content instead of the default codepage.
On Windows 11 24H2, netsh.exe now outputs messages in UTF-8 instead of ANSI. In the Japanese (CP932) environment, localized messages are output in UTF-8, but when converting from AnsiString to (Unicode)String, the default codepage (932) is applied, resulting in incorrect conversion (garbled characters).
Add the CodePage property to JvCreateProcess and apply the received message to the specified codepage before converting it to UnicodeString.
You can set the codepage to 65001 (UTF-8) to ensure proper conversion when a console application outputs messages in UTF-8.